Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1328

reference: 855-tree-1
name: 1328
tree-preservation-order: undefined
855-tpo-1
uprn: 10013683669;10013683670
address-text: 20 Harrison Way, Havant, PO9 5FD;22 Harrison Way, Havant, PO9 5FD
point: POINT (-0.962333 50.867199)
geometry: MULTIPOLYGON (((-0.962205 50.867185,-0.962211 50.867210,-0.962229 50.867233,-0.962256 50.867251,-0.962292 50.867263,-0.962331 50.867267,-0.962371 50.867264,-0.962407 50.867252,-0.962435 50.867235,-0.962454 50.867212,-0.962461 50.867187,-0.962455 50.867162,-0.962438 50.867140,-0.962410 50.867121,-0.962374 50.867110,-0.962335 50.867105,-0.962295 50.867109,-0.962259 50.867120,-0.962231 50.867138,-0.962212 50.867160,-0.962205 50.867185)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL